Repository navigation
Conversation
size-limit report 📦
|
3dfbedc to
e9cafef
Compare
e9cafef to
aa89862
Compare
aa89862 to
3b1e94f
Compare
3b1e94f to
f8eea69
Compare
f8eea69 to
bb2078f
Compare
bb2078f to
9c5e4d6
Compare
9c5e4d6 to
62ef54d
Compare
|
bugbot run |
62ef54d to
40a29bc
Compare
|
bugbot run |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 40a29bc. Configure here.
40a29bc to
fcb4724
Compare
fcb4724 to
acf7baf
Compare
3c79c4e to
cd1c651
Compare
941ca1d to
e2905ce
Compare
e2905ce to
3e95627
Compare
|
Semgrep found 1 🟠 High severity issue identified in your code: Risk: Affected versions of h3 are vulnerable to Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling'). The readRawBody function in h3 performs a strict, case-sensitive check for "chunked" in the Transfer-Encoding header. If an attacker sends a mixed-case value (e.g. "Transfer-Encoding: ChuNked") and no Content-Length, h3 will assume an empty body, immediately process the request, and leave the real payload data on the socket. When h3 is deployed behind a Layer 4 proxy (such as AWS NLB or raw TCP proxies that don't normalize headers), this enables a classic TE.TE HTTP request smuggling attack—allowing an attacker to bypass WAFs or desynchronize and poison other users' connections. Fix: Upgrade this library to at least version 1.15.5 at sentry-javascript/yarn.lock:16852. Reference(s): https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-2737, GHSA-mp2g-9vg9-f4cg, CVE-2026-23527 |
4d706ab to
5e25502
Compare
5e25502 to
a247d5b
Compare
a247d5b to
bbc97ee
Compare
bbc97ee to
91851de
Compare
91851de to
fda291a
Compare
fda291a to
ccccc31
Compare
ccccc31 to
28d348f
Compare
28d348f to
f1d1f8e
Compare
The Sentry middleware runs first and answers tunnel requests. The integration hands Astro's `base` and `trailingSlash: 'always'` to both SDKs, so `tunnel: true` follows Astro's routing without repeating them.
…orks on a cold server
This reverts commit 6647a68. The middleware module ran the inline default init a second time, and running the init before a cold non-page request is a gap develop has for every server request, not one the tunnel adds.
The server's tunnel base path only reached `@sentry/astro`'s own server init. On Workers the client comes from `@sentry/cloudflare`, so the browser posted under `base` and got a 404. The server side of the tunnel options module now goes through core's managed tunnel defaults, and the Worker entry imports it first.
f1d1f8e to
740bba2
Compare
This PR adds the tunnel wiring to the astro SDK. We already had a global middleware active, so it works by adding logic to check if the incoming request is a tunnel request and if it is, then it will be handled.
This also respects the decision made earlier to follow the base path configured by the user.
closes #25463